Skip to content

Conversation

@carlesarnal
Copy link
Contributor

@carlesarnal carlesarnal commented Apr 17, 2024

Check list:

Your pull request:

  • targets the development branch
  • uses the 999-SNAPSHOT version of Quarkus
  • has tests (mvn clean test)
  • works in native (mvn clean package -Pnative)
  • has integration/native tests (mvn clean verify -Pnative)
  • makes sure the associated guide must not be updated
  • links the guide update pull request (if needed)
  • updates or creates the README.md file (with build and run instructions)
  • for new quickstart, is located in the directory component-quickstart
  • for new quickstart, is added to the root pom.xml and README.md

Opening as a replacement of #1361 targeting development

@quarkus-bot

This comment has been minimized.

@carlesarnal carlesarnal force-pushed the json-schema-kafka-quickstart branch from 1ad6e60 to bcf109a Compare July 23, 2024 11:06
@quarkus-bot

This comment has been minimized.

@carlesarnal carlesarnal force-pushed the json-schema-kafka-quickstart branch from bcf109a to fdc8f20 Compare July 24, 2024 07:47
@quarkus-bot

This comment has been minimized.

@carlesarnal carlesarnal force-pushed the json-schema-kafka-quickstart branch from fdc8f20 to 1688afa Compare July 24, 2024 08:54
@carlesarnal carlesarnal force-pushed the json-schema-kafka-quickstart branch from 1688afa to eb28de3 Compare July 24, 2024 09:09
@quarkus-bot

This comment has been minimized.

@quarkus-bot
Copy link

quarkus-bot bot commented Jul 24, 2024

Status for workflow Pull Request Build - development

This is the status report for running Pull Request Build - development on commit eb28de3.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@gsmet
Copy link
Member

gsmet commented Apr 22, 2025

@cescoffier @ozangunalp could you have a look at this one? It looks interesting and maybe something we should document in the guides, if we get it in?

Copy link
Member

@cescoffier cescoffier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. I'm wondering if some properties can be deduced automatically.


mp.messaging.outgoing.movies.apicurio.registry.auto-register=true
mp.messaging.outgoing.movies.apicurio.registry.artifact.schema.location=json-schema.json
mp.messaging.outgoing.movies.value.serializer=io.apicurio.registry.serde.jsonschema.JsonSchemaKafkaSerializer
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of sad we can't detect these automatically.
@ozangunalp WDYT?

@cescoffier
Copy link
Member

The guide already exists: https://quarkus.io/guides/kafka-schema-registry-json-schema

@ozangunalp
Copy link
Contributor

Was the provided schema expected to validate the json?

The schema contains an error, (I guess explicitly) but I don't see that produce is rejected with schema validation error. It needs to set "required" properties in order to validate the content.

@cescoffier yes, I think we can emit default values for serde when the property apicurio.registry.artifact.schema.location is present.

mp.messaging.outgoing.movies.apicurio.registry.auto-register=true
mp.messaging.outgoing.movies.apicurio.registry.artifact.schema.location=json-schema.json
mp.messaging.outgoing.movies.value.serializer=io.apicurio.registry.serde.jsonschema.JsonSchemaKafkaSerializer
mp.messaging.outgoing.movies.value.deserializer=io.apicurio.registry.serde.jsonschema.JsonSchemaKafkaDeserializer
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line isn't needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants